Skip to content

Conversation

@shivamdesai04
Copy link

No description provided.

…eMachine API to make StateMachine more reusable
…ate into CoreProto.proto and ControlMessage.proto. Generate new .py and pyi files
… respective serialhandler thread (radio/uart) with the state machine manager. Adjust main function to only call the radio_thread and the state_machine manager thread to ensure they are using the same queue.
…e not include logic for TIMEOUT. Have not tested.
…en mock sending out the msg to the DMB, then put the system in WAIT state. The Wait state will resend the same msg for now, until TIMEOUT logic is figured out next week.
…e to switch state and notify serial outgoing thread. Added self.serial_event.wait() after checking if the queue is not empty so we can notify the outgoing thread. The workflow goes as follows: serial_rx_thread receives a message (ACK/NAK) -> set a flag and notify the state machine -> state machine change state and notify the outgoing thread -> outgoing thread process the state change
…e. It should go serial handler incoming thread -> state machine -> serial handler outgoing thread -> state machine. The order of operation is shown here when running it on debug view. However, there is a race condition when the serial handler incoming thread and the serial handler outgoing thread are updating the serial event queue at the same time, causing the state machine to only see the event in the queue before the serial handler outgoing thread gets a chance to update the queue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants